System of Migration and Validation

ABSTRACT

Disclosed herein are system, method, and computer program product embodiments system of migration and validation. An embodiment operates by receiving an indication of a plurality of documents for migration from a legacy data format to a new data format of a computing system. A first set of data statistics corresponding to a selected one of the subset of documents prior to a performance of the migration, and a second set of data statistics corresponding to the selected document after the performance of the migration are determined. Both the first set of data statistics and the second set of data statistics side-by-side for the selected document are displayed. An indication whether the migration is validated or invalidated is received.

BACKGROUND

As business and technical systems are upgraded and changed, often timesexisting business documents need to be reformatted or migrated from acurrent or legacy document format to a new document format. One of thechallenges in performing migrations is ensuring that no data from theexisting documents is lost during the migration process from the legacyformat to the new format. To ensure no data is permanently lost, themigration process should be validated prior to removing the old orexisting business data in the legacy format.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 is a block diagram showing example operations related to a systemof migration and validation, according to some embodiments.

FIG. 2 is a flowchart illustrating a process for providing a system ofmigration and validation, according to some embodiments.

FIG. 3 is an example computer system useful for implementing variousembodiments.

In the drawings, like reference numbers generally indicate identical orsimilar elements. Additionally, generally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

DETAILED DESCRIPTION

Provided herein are system, apparatus, device, method and/or computerprogram product embodiments, and/or combinations and sub-combinationsthereof, for a system of migration and validation.

FIG. 1 is a block diagram 100 showing example operations related to asystem of migration and validation, according to some embodiments.Migration and validation system (MVS) 102 may coordinate the migrationand validation of documents from a legacy format 104 to a new format106.

As business and technical systems are upgraded and changed, often timesexisting business documents 108 need to be reformatted, converted, ormigrated from a current or legacy format 104 to a new format 106. Thedata format could be changed for any number of reasons, including butnot limited to, adapting to new versions of software, improvingreadability or usability by an end user, or reducing storagerequirements for information, etc. One of the challenges in performingmigrations is ensuring that no data from the existing documents 110 islost during the migration process from the legacy format 104 to the newformat 106. To ensure no data is permanently lost, MVS 102 enables usersto validate that a document in the new format 108B matches orcorresponds to the document in the legacy format 108A or that there areno other unexpected changes.

MVS 102 may allow real-time migration of live or active documents(documents that are being accessed or are otherwise accessible to usersof a computing system). For example, MVS 102 may enable visitors of awebsite to continue accessing documents 110 as they are converted ormigrated from legacy format 104 to new format 106. MVS 102 may manageaccess to both legacy documents 108A and newly formatted documents 108B,by maintaining accessibility to only one version of the document (via anactive doc flag 122) at any given time. MVS 102 may ensure that systemusers do not see two different versions of the same document 108 in thelive system that is being accessed or that may remain accessiblethroughout the migration and validation processes.

After receiving a validation indication 120 that the migration fromdocument 108A to document 108B has been validated (e.g., there are noerrors in document 108B), MVS 102 may activate the new version of thedocument 108B by setting the active doc flag 122 and document 108A maycorrespondingly be deactivated. If, however, the migration to document108B is invalidated by validation indication 120, the migration may becancelled, postponed, or rolled back, and users may continue to accessthe active document 108A without any interruption of service oraccessibility.

In an embodiment, a migration system (not shown) may be responsible forconverting document 108 from legacy format 104 to new format 106. Themigration system may retrieve legacy documents from a legacy database110, convert the documents into new format 106, and store them in a newdatabase 112. In an embodiment, legacy database 110 and new database 112may be part of the same database, memory, storage, or computing device,may be communicably coupled, or may exist separately from one another.MVS 102 may coordinate with the migration system, collecting statistics118 about the documents 108 being converted both prior to and after theconversion or migration between data formats 104, 106. MVS 102 maypresent the collected statistics 118 in a side-by-side (or top-bottom)display for validation by one or more users or administrators.

Statistics 118 may include any enumerated or quantifiable informationthat can be collected, aggregated, and/or otherwise processed about adocument 108 both before and after migration or conversion from legacyformat 104 to new format 106. Example statistics 118 include a wordcount, page count, link count, comment count, and image count. Oneskilled in the relevant arts would appreciate that other informationabout document 108 may be included in statistics 118. Other exampleinformation includes how many revisions or translations a document 108has undergone, or how many business objects (such as actual or usecases) to which the document 108 is linked, attached, or otherwiserelated.

By way of non-limiting example, the word count may include a count ofhow many words appear in document 108 (or a particular portion thereof).The page count may include how many pages or screens the document spansor is otherwise displayed across. The link count may include how manyhyperlinks are included with content 114 of the document or areotherwise associated with document 108. The comment count may includehow many user comments or other updates are displayed or associated withdocument 108. The image count may include how many images appear withincontent 114 of document 108.

Legacy statistics 118A may include the statistics collected prior tomigration about the document 108, or from a first version of thedocument 108A in the legacy format 104. New statistics 118 may includethe same statistics collected after the migration of document 108 intonew format 106. For example, a word count may be performed both beforeand after the migration of document 108 to new format 106.

In an embodiment, MVS 102 may display legacy statistics 118A and newstatistics 118B side-by-side (or top-down) enabling a comparison ofthese details both before and after migration. In an embodiment, MVS 102may provide a visual indicator for any new statistics 118B which do notmatch corresponding legacy statistics 118A. In an embodiment, a variancein the statistics 118A, 118B may indicate that there is a potentialissue or change that occurred during the migration of document 108.Providing statistics side-by-side may enable an easy comparison for auser who is validating the migration of document 108.

In an embodiment, MVS 102 may flag if the word count changes betweendocument 108A and document 108B. A validating user, may then determinewhether or not the change in word count was expected (as part of the newformat 106 change) or unexpected (indicating there may be an issue withthe migration that needs to be resolved). For example, changing the fontsize should not change the word count. As such, a variance in wordcounts may indicate that something the migration needs to be addressedor corrected. However, if all new documents (in new format 106) arelimited to 500 words, then variance in word count from 863 words fordocument 108A to 500 words for document 108B may indicate that themigration has performed successfully.

In addition to displaying statistics 118 for comparison as part of thevalidation process, MVS 102 may also display the actual content 114 ofdocument 108 both before 114A and after migration 114B. Content 114 mayinclude any text, images, videos, or links within a document or webpage.MVS 102 may enable a validating user to see documents 108A and 108B asthey would appear to an end user accessing the computing system orwebsite.

In an embodiment, new format 106 may change the font type, font size, orother appearance or arrangement of content of a document from legacyformat 104. MVS 102 may provide live or simulated-live versions of thedocument, so that a user validating the migrated document 108B can seehow an end user would see or access document 108 both before and aftermigration, across one or more different device types or operatingsystems. For example, MVS 102 may provide a display on how content 114would appear on a laptop, tablet, and mobile phone. In an embodiment,content 114 may include comments, updates, social media tags/references,or other feed items that were appended to or otherwise associated with adocument 108 after it was initially published or otherwise made live oraccessible to end users.

MVS 102 may enable an administrator or other user(s) to easily comparethe side-by-side display of information to determine whether or not themigration of document 108 was successful. In an embodiment, MVS 102 mayperform an automated comparison and highlight any differences betweenlegacy format 104 and new format 106. For example, MVS 102 may providean indication that font type has changed, but font size has stayed thesame. Or, for example, MVS 102 may provide an indication that the wordscount before and after the migration has changed or does not match. MVS102 may provide a visual indicator that indicates if any content 114 wasdeleted, moved, or added in the conversion to new format 106. If thevalidating user notices any differences that are unacceptable, the usermay invalidate the migration. If however, everything appears as it wassupposed to be in document 108B, the migration may be validated.

If the migration is invalidated, the migration system or migrationadministrator may be notified of the invalidation. In an embodiment, MVS102 may enable a validating user to submit comments or an indication asto why document 108B was invalidated. In an embodiment, document 108Bmay need to be validated or invalidated by multiple users prior to afinal validation or invalidation determination may be made. For example,three different users may each provide a separate or independentvalidation indication 120 on document 108 before MVS 102 marks themigration of document as being validated or invalidated.

MVS 102 may receive a validation indication 120 from each of thevalidating users, and if two out of the three users validates orapproves the migration. MVS 102 may validate the migration for document108. Or, for example, MVS 102 may require validation from all thereviewing users to validate the migration of document 108, and if anyuser invalidates the migration, then the migration may be invalidated.

Similarly, multiple different documents 108 may need to be validatedprior to MVS 102 determining whether or not the entire migration wasvalidated. For example, a sampling or subset of ten documents, from adatabase 110 of one thousand documents, may be selected by a validatinguser or at random may be provided for validation by a user prior todetermining whether or not the migration is successfully validated orinvalidated.

In an embodiment, validation may be performed on the selected subset ofdocuments 108 from legacy database 110 prior to performing a migrationon the remaining documents. For example, legacy database 110 may include1000 documents, but a subset of 20 documents may be selected formigration and validation prior to performing a migration of theremaining documents. This may enable MVS 102 to save processing cyclesthat may otherwise be required to migrate all of the documents of legacydatabase 110 prior to validation if the migration is invalidated. Theselected subset of documents may all be migrated together (prior tovalidation of any particular document), or may be migrated one-by-one,only upon validation of a previously validated migrated document.

In an embodiment, documents of legacy database 110 may be associatedwith varying document types 124. Document type 124 may indicate afunction and/or format of the document 108. Example document types 124includes sales orders, employee reimbursement forms, spreadsheets, webpages, word processing documents, HTML (hyper-text markup language)documents, and XML (extensible markup language) documents.

Using doc type 124, a migration may be validated or invalidated on adocument-type by document-type basis. Then for example, even thoughthere may be millions of legacy documents 110 for migration, thedocuments may be further separated or grouped by doc type 124. Then,migration of for each doc type 124 may be individually validated orinvalidated.

Performing migration and validation based on doc type 124 may savecomputing cycles and processing resources in debugging, recompiling,executing the migration of documents 108. For example, rather thanmigrating all of the documents 110 at once, each document type 124 mayindividually be validated and migrated. Then, for example, if aparticular migration for a particular type 124 is invalidated, thaterror could be fixed across the various migrations for the otherdocument types 124 before those migrations are performed or validated.Otherwise if an error is found after a migration of all the documents,then all the documents for which processing cycles were used togenerate, may then need to be deleted, only to be re-generated under anew migration and validation process after the error has been corrected.This could waste a lot of unnecessary computing cycles in the generationand deletion or garbage collection of migrated documents which have notbeen validated.

In an embodiment, if the migration of document(s) 108 is invalidated,then the migration process may be updated (to correct whatever errorsmay have been detected), and MVS 102 may perform a re-validationprocess. In an embodiment, re-validation may include the same documentsbeing selected for re-validation. Or, for example, in anotherembodiment, a larger or different selection of documents may be selectedor required for re-validation.

In an embodiment, MVS 102 may enable an administrator or user tore-migrate one or more documents 108. For example, if a discrepancy indocument 108B is noticed during the validation process, a user mayrequest a re-migration. Then, for example, MVS 102 may provide the userwith the legacy document 104A and the re-migrated document 108B. In anembodiment, MVS 102 may provide access to the intermediately migrateddocument 108B as well. Then, for example, the user may compare theintermediately and most recently migrated documents 108 to determine ifany differences exist between the documents.

When the migration has been validated, the remaining documents fromlegacy database 110 (which were not already converted) may be migratedto new database 112 (in new format 106) and/or otherwise made active122. In an embodiment, once migration of all documents is complete (andthe selected subset have been validated), the legacy documents 110 maybe deleted or otherwise marked for deletion.

As noted above, legacy database 110 may include documents that arecurrently active or accessible to users of a computing system. The usersmay include clients, customers, employees, visitors of a website, orother users. For example, the documents 110 may include knowledge basedocuments that enable users to find answers to commonly asked questionsby typing in searches or queries on a website. These documents may beconsidered ‘live’ or currently accessible to users who may be searchingfor and/or accessing one or more of the documents.

One feature of a successful migration of documents between formats is toensure that valuable information is not lost during the migrationprocess. MVS 102 enables a user to validate that the migration processhas performed correctly, without the loss of any valuable information,by collecting and providing a side-by-side display of the document 108and key statistics or features 118 both before and after the migration.Then, only after, a document 108 has been validated are the migrationsperformed for the remaining documents 110 and are the migrated documents112 made active and the legacy formatted documents may be markedinactive or no longer be made accessible (to avoid providing user accessto a document 108 in two different formats).

FIG. 2 is a flowchart illustrating a process 200 for providing migrationand validation, according to some embodiments. Method 200 can beperformed by processing logic that can comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions executing on a processing device), or acombination thereof. It is to be appreciated that not all steps may beneeded to perform the disclosure provided herein. Further, some of thesteps may be performed simultaneously, or in a different order thanshown in FIG. 2, as will be understood by a person of ordinary skill inthe art.

At 210, an indication for migration of a plurality of documents from alegacy data format to a new data format of a computing system isreceived. For example, MVS 102 may receive an indication that legacydocuments 110 may be converted from legacy format 104 to new format 106.The documents of legacy database 110 may include live or activedocuments that are currently being accessed or accessible to end usersof a computing system or website. In an embodiment, the migration andvalidation may be performed via MVS 102 while maintaining the activestatus of at least one version of the documents throughout the process.

At 220, a first set of data statistics corresponding to a selected oneof the subset of documents prior to a performance of the migration isdetermined. For example, MVS 102 may scan or analyze document 108A ormetadata associated with document 108A to determine legacy statistics118A about the active document 108A prior to migration.

At 230, a second set of data statistics corresponding to the selecteddocument after the performance of the migration is determined. Forexample, MVS 102 may scan or analyze document 108B or metadataassociated with document 108B to determine new statistics 118B about theinactive document 108B prior to migration.

At 240, both the first set of data statistics and the second datastatistics are displayed side-by-side for the selected document. Forexample, MVS 102 may display legacy statistics 118A and new statistics118B side-by-side for a user comparison and validation of the migrationprocess. During the validation process, MVS 102 may maintain the activestatus 122 or accessibility of document 108A until document 108B isvalidated and made active or accessible 122.

At 250, an indication of validation of the migration indicating whetherthe migration is validated or invalidated is received. For example, MVS102 may receive validation indication 120 indicating whether or not themigration or conversion of document 108 from legacy format 104 to newformat 106 is validated. Based on a validation of the migration,document 108B may be made active 122 and documents 108A may be madeinactive. Based on an invalidation of the migration, document 108A mayremain active to the users accessing legacy database 110.

Various embodiments may be implemented, for example, using one or morewell-known computer systems, such as computer system 300 shown in FIG.3. One or more computer systems 300 may be used, for example, toimplement any of the embodiments discussed herein, as well ascombinations and sub-combinations thereof.

Computer system 300 may include one or more processors (also calledcentral processing units, or CPUs), such as a processor 304. Processor304 may be connected to a communication infrastructure or bus 306.

Computer system 300 may also include user input/output device(s) 303,such as monitors, keyboards, pointing devices, etc., which maycommunicate with communication infrastructure 306 through userinput/output interface(s) 302.

One or more of processors 304 may be a graphics processing unit (GPU).In an embodiment, a GPU may be a processor that is a specializedelectronic circuit designed to process mathematically intensiveapplications. The GPU may have a parallel structure that is efficientfor parallel processing of large blocks of data, such as mathematicallyintensive data common to computer graphics applications, images, videos,etc.

Computer system 300 may also include a main or primary memory 308, suchas random access memory (RAM). Main memory 308 may include one or morelevels of cache. Main memory 308 may have stored therein control logic(i.e., computer software) and/or data.

Computer system 300 may also include one or more secondary storagedevices or memory 310. Secondary memory 310 may include, for example, ahard disk drive 312 and/or a removable storage device or drive 314.Removable storage drive 314 may be a floppy disk drive, a magnetic tapedrive, a compact disk drive, an optical storage device, tape backupdevice, and/or any other storage device/drive.

Removable storage drive 314 may interact with a removable storage unit318. Removable storage unit 318 may include a computer usable orreadable storage device having stored thereon computer software (controllogic) and/or data. Removable storage unit 318 may be a floppy disk,magnetic tape, compact disk, DVD, optical storage disk, and/any othercomputer data storage device. Removable storage drive 314 may read fromand/or write to removable storage unit 318.

Secondary memory 310 may include other means, devices, components,instrumentalities or other approaches for allowing computer programsand/or other instructions and/or data to be accessed by computer system300. Such means, devices, components, instrumentalities or otherapproaches may include, for example, a removable storage unit 322 and aninterface 320. Examples of the removable storage unit 322 and theinterface 320 may include a program cartridge and cartridge interface(such as that found in video game devices), a removable memory chip(such as an EPROM or PROM) and associated socket, a memory stick and USBport, a memory card and associated memory card slot, and/or any otherremovable storage unit and associated interface.

Computer system 300 may further include a communication or networkinterface 324. Communication interface 324 may enable computer system300 to communicate and interact with any combination of extemal devices,external networks, extemal entities, etc. (individually and collectivelyreferenced by reference number 328). For example, communicationinterface 324 may allow computer system 300 to communicate with externalor remote devices 328 over communications path 326, which may be wiredand/or wireless (or a combination thereof), and which may include anycombination of LANs, WANs, the Internet, etc. Control logic and/or datamay be transmitted to and from computer system 300 via communicationpath 326.

Computer system 300 may also be any of a personal digital assistant(PDA), desktop workstation, laptop or notebook computer, netbook,tablet, smart phone, smart watch or other wearable, appliance, part ofthe Internet-of-Things, and/or embedded system, to name a fewnon-limiting examples, or any combination thereof.

Computer system 300 may be a client or server, accessing or hosting anyapplications and/or data through any delivery paradigm, including butnot limited to remote or distributed cloud computing solutions; local oron-premises software (“on-premise” cloud-based solutions); “as aservice” models (e.g., content as a service (CaaS), digital content as aservice (DCaaS), software as a service (SaaS), managed software as aservice (MSaaS), platform as a service (PaaS), desktop as a service(DaaS), framework as a service (FaaS), backend as a service (BaaS),mobile backend as a service (MBaaS), infrastructure as a service (laaS),etc.); and/or a hybrid model including any combination of the foregoingexamples or other services or delivery paradigms.

Any applicable data structures, file formats, and schemas in computersystem 300 may be derived from standards including but not limited toJavaScript Object Notation (JSON), Extensible Markup Language (XML), YetAnother Markup Language (YAML). Extensible Hypertext Markup Language(XHTML), Wireless Markup Language (WML), MessagePack, XML User InterfaceLanguage (XUL), or any other functionally similar representations aloneor in combination. Alternatively, proprietary data structures, formatsor schemas may be used, either exclusively or in combination with knownor open standards.

In some embodiments, a tangible, non-transitory apparatus or article ofmanufacture comprising a tangible, non-transitory computer useable orreadable medium having control logic (software) stored thereon may alsobe referred to herein as a computer program product or program storagedevice. This includes, but is not limited to, computer system 300, mainmemory 308, secondary memory 310, and removable storage units 318 and322, as well as tangible articles of manufacture embodying anycombination of the foregoing. Such control logic, when executed by oneor more data processing devices (such as computer system 300), may causesuch data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments of this disclosure using data processing devices, computersystems and/or computer architectures other than that shown in FIG. 3.In particular, embodiments can operate with software, hardware, and/oroperating system implementations other than those described herein.

It is to be appreciated that the Detailed Description section, and notany other section, is intended to be used to interpret the claims. Othersections can set forth one or more but not all exemplary embodiments ascontemplated by the inventor(s), and thus, are not intended to limitthis disclosure or the appended claims in any way.

While this disclosure describes exemplary embodiments for exemplaryfields and applications, it should be understood that the disclosure isnot limited thereto. Other embodiments and modifications thereto arepossible, and are within the scope and spirit of this disclosure. Forexample, and without limiting the generality of this paragraph,embodiments are not limited to the software, hardware, firmware, and/orentities illustrated in the figures and/or described herein. Further,embodiments (whether or not explicitly described herein) havesignificant utility to fields and applications beyond the examplesdescribed herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments can performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedcan include a particular feature, structure, or characteristic, butevery embodiment can not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein. Additionally, some embodiments can bedescribed using the expression “coupled” and “connected” along withtheir derivatives. These terms are not necessarily intended as synonymsfor each other. For example, some embodiments can be described using theterms “connected” and/or “coupled” to indicate that two or more elementsare in direct physical or electrical contact with each other. The term“coupled,” however, can also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other.

The breadth and scope of this disclosure should not be limited by any ofthe above-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. A method, comprising: receiving an indication ofa plurality of documents for migration from a legacy data format to anew data format of a computing system, wherein one or more of theplurality of documents are accessible to one or more users in the legacydata format; determining a first set of data statistics corresponding toa selected one of the subset of documents prior to a performance of themigration; determining a second set of data statistics corresponding tothe selected document after the performance of the migration; displayingboth the first set of data statistics and the second set of datastatistics side-by-side for the selected document, wherein a firstversion of the selected document in the legacy format remains accessibleto the one or more users, wherein a second version of the selecteddocument in the new data format is not accessible to the one or moreusers, and wherein both the first and second versions of the selecteddocument are accessible for validation; and receiving, responsive to thedisplaying, an indication whether the migration is validated orinvalidated, wherein upon indication that the migration has beenvalidated, the second version of the document is made accessible to theone or more users and the first version of the document is madeinaccessible.
 2. The method of claim 1, further comprising: marking thefirst version of the document for deletion after the first version ofthe document is made inaccessible.
 3. The method of claim 1, wherein thereceiving the indication further comprises: marking the second versionof the document for deletion based upon the indication that themigration is invalidated, wherein the first version of the documentremains made accessible.
 4. The method of claim 1, wherein the both thefirst set of data statistics and the second set of data statisticsinclude one or more of a version count, image count, word count, or feeditem count.
 5. The method of claim 1, further comprising: determining adocument type of the selected document; and determining one or moreother documents of the plurality of documents with the same documenttype, wherein upon the indication that the migration is validated, asecond version of the determined one or more other documents with thesame document type is migrated from the legacy data format to the newdata format and made accessible to the one or more users.
 6. The methodof claim 5, wherein the plurality of documents includes one otherdocument type different from the document type of the selected documentthat is not validated by the indication.
 7. The method of claim 6,wherein the determining the first set of data statistics, determiningthe second set of data statistics, the displaying, and the receiving theindication of validation is performed for a selected document of theother document type.
 8. The method of claim 1, wherein the displayingcomprises: displaying content from the first version of the selecteddocument side-by-side content from the second version of the selecteddocument.
 9. The method of claim 1, wherein the displaying comprises:determining a variance between the first set of data statistics and thesecond set of data statistics; and displaying a visual indicator of thevariance.
 10. A system, comprising: a memory; and at least one processorcoupled to the memory and configured to: receive an indication of aplurality of documents for migration from a legacy data format to a newdata format of a computing system, wherein one or more of the pluralityof documents are accessible to one or more users in the legacy dataformat; determine a first set of data statistics corresponding to aselected one of the subset of documents prior to a performance of themigration; determine a second set of data statistics corresponding tothe selected document after the performance of the migration; displayboth the first set of data statistics and the second set of datastatistics side-by-side for the selected document, wherein a firstversion of the selected document in the legacy format remains accessibleto the one or more users, wherein a second version of the selecteddocument in the new data format is not accessible to the one or moreusers, and wherein both the first and second versions of the selecteddocument are accessible for validation; and receive, responsive to thedisplaying, an indication whether the migration is validated orinvalidated, wherein upon indication that the migration has beenvalidated, the second version of the document is made accessible to theone or more users and the first version of the document is madeinaccessible.
 11. The system of claim 10, wherein the processor isfurther configured to: marking the first version of the document fordeletion after the first version of the document is made inaccessible.12. The system of claim 10, wherein the processor is further configuredto: marking the second version of the document for deletion based uponthe indication that the migration is invalidated, wherein the firstversion of the document remains made accessible.
 13. The system of claim10, wherein the both the first set of data statistics and the second setof data statistics include one or more of a version count, image count,word count, or feed item count.
 14. The system of claim 10, wherein theprocessor is further configured to: determine a document type of theselected document; and determine one or more other documents of theplurality of documents with the same document type, wherein upon theindication that the migration is validated, a second version of thedetermined one or more other documents with the same document type ismigrated from the legacy data format to the new data format and madeaccessible to the one or more users.
 15. The system of claim 14, whereinthe plurality of documents includes one other document type differentfrom the document type of the selected document that is not validated bythe indication.
 16. The system of claim 10, wherein the processconfigured to display is further configured to: display content from thefirst version of the selected document side-by-side content from thesecond version of the selected document.
 17. The system of claim 10,wherein the process configured to display is further configured to:determine a variance between the first set of data statistics and thesecond set of data statistics; and display a visual indicator of thevariance.
 18. A non-transitory computer-readable device havinginstructions stored on a memory thereon that when executed by at leastone processor of the device, causes the at least one processor toperform operations comprising:
 19. receiving an indication of aplurality of documents for migration from a legacy data format to a newdata format of a computing system, wherein one or more of the pluralityof documents are accessible to one or more users in the legacy dataformat; determining a first set of data statistics corresponding to aselected one of the subset of documents prior to a performance of themigration; determining a second set of data statistics corresponding tothe selected document after the performance of the migration; displayingboth the first set of data statistics and the second set of datastatistics side-by-side for the selected document, wherein a firstversion of the selected document in the legacy format remains accessibleto the one or more users, wherein a second version of the selecteddocument in the new data format is not accessible to the one or moreusers, and wherein both the first and second versions of the selecteddocument are accessible for validation; and receiving, responsive to thedisplaying, an indication whether the migration is validated orinvalidated, wherein upon indication that the migration has beenvalidated, the second version of the document is made accessible to theone or more users and the first version of the document is madeinaccessible.
 20. The device of claim 19, wherein the both the first setof data statistics and the second set of data statistics include one ormore of a version count, image count, word count, or feed item count.